IBIS Macromodel Task Group

Meeting date: 19 Dec 2006

Members (asterisk for those attending):
* Arpad Muranyi, Intel Corp.
* Barry Katz, SiSoft
* Bob Ross, Teraspeed Consulting Group
* Doug White, Cisco Systems
* Hemant Shah, Cadence Design Systems
* Ian Dodd, Mentor Graphics
  Joe Abler, IBM
  John Angulo
  John Shields, Mentor Graphics
  Ken Willis, Cadence Design Systems
* Kumar, Cadence Design Systems
* Lance Wang, Cadence Design Systems
* Michael Mirmak, Intel Corp.
* Mike LaBonte, Cisco Systems
  Patrick O'Halloran, Tiburon Design Automation
  Paul Fernando, NCSU
  Randy Wolff, Micron Technology
  Richard Ward, Texas Instruments
  Sanjeev Gupta, Agilent
  Shangli Wu, Cadence
* Todd Westerhoff, SiSoft
* Walter Katz, SiSoft
  Vuk Borich, Agilent
  Vikas Gupta, Xilinx

-------------
Review of ARs:

- Mike update macro library documentation
  Will send I/O doc to Arpad for review soon.

- Kumar: Incorporate some of the terminology, as presented in the
  SiSoft presentation, into the API proposal, especially into
  the examples.
  - done

-------------
New Discussion:

Mike will add Kumar and Hemant to the email list.

Everyone agrees with linear/time-invariant assumption for the API proposal.
If system is not LTI, how do we estimate how far off the results will be?
Ian may have an algorithm to determine if a model is LTI.
GTL buffer may be too non-linear for this approach.
Pulse response can be used to create a step response - will this match an original step response?
If differential rise edge is different from fall edge, this may cause problems for analysis.
We might want to limit on 7GB serdes, LTI, to allow tools to analyze any way they want.
LTI will not work at lower frequencies.

Walter: Models should be supplied with a test deck and golden waveforms.
IBIS Golden waveforms are use for silicon lab measurements, may not work for channel analysis.

S-params give characteristics of "ideal" impulse response, but only as far as the frequency range allows.

New Cadence presentation using Todd's terminology
If 3 == 4, then 1 == 2 ... yeah, that's the ticket

TX should not optimize itself, EDA tool should do it.
SiSoft proposes that API not needed to model TX

-------------

Next meeting: Tuesday 09 Jan 2006 12:00pm PT